Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for --spec CLI option #167

Merged
merged 2 commits into from
Nov 30, 2023

Conversation

ryanolson-aumni
Copy link
Contributor

As an alternative to -d, you can pass spec file paths (just like you would in Cypress). If --spec is present, it will use that to determine which tests to run.

Resolves #155

As an alternative to -d, you can pass spec file paths (just like you
would in Cypress). If --spec is present, it will use that to determine
which tests to run.

Resolves tnicola#155
@AlinaSkilsaraFreshcode
Copy link

Hi guys, thank you for your update, it's very useful. When will it be merged?

@valipopa
Copy link

@IkaroSantos @ryanolson-aumni hey there, any updates on this one? could really use it, because even if all test suites in directory pass, build fails because not all found specs provide results. Thanks, appreciate it!

@roxaaams
Copy link

roxaaams commented Nov 8, 2023

@ryanolson-aumni @IkaroSantos can we have this PR merged please?

@tnicola tnicola merged commit 7b1f7ee into tnicola:master Nov 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot exclude tests with Cypress command arguments (-a)
6 participants